Skip to main content

APPENDIX - TMP Structure

Intent

This appendix outlines a typical Tactical Mission Plan (TMP) structure. The TMP is the authoritative planning product produced by the Mission Planning Cell (MPC) and used by the Mission Element (ME) to execute the mission.

The TMP must fully describe the mission, environment, adversary, effects, execution concept, required capabilities, control measures, contingencies, and assessment in a way that is executable without interpretation.

1 - Mission​

Purpose

Define what must be accomplished and why, bound the tactical problem, and define what “done” looks like. This section sets the foundation for all downstream TMP content (Environment, Enemy, Effects, Capabilities, Plan, Phasing, Contracts, Contingencies, Assessment).

1.1 - Required Information​

  • Situation: Concise narrative derived from OPORD/TASKORD/FRAGORD/SPINS that answers:
    • Who Is Tasked
    • What They Are Tasked To Do
    • Why They Are Tasked To Do It
  • Commander's Intent: Tasking commander's intent (not the MPC's). If classified, this may drive TMP classification.
  • Operational Tasks (OTs): What the unit must accomplish (not how). Include:
    • Specified Tasks: Tasks explicitly stated in the tasking order
    • Implied Tasks: Unstated tasks required to accomplish specified tasks and generate desired effects
  • End State: Observable, assessable conditions that indicate mission completion.
  • Limitations:
    • Constraints (Must-Do): Actions the ME must take (derived from orders/SPINS/ROE)
    • Restraints (Must-Not-Do): Actions the ME is prohibited from taking
  • Information:
    • Facts: Verified information that materially impacts planning or execution
    • Assumptions: Unverified information that impacts mission success; assumptions must be validated via RFIs/FFIRs/partner coordination when possible, and any assumption that remains unverified must have a corresponding contingency
  • Mission Scope and Boundaries: Explicitly state what the mission does not include to prevent scope creep.
  • Authority and Decision Boundaries: Clarify who can decide what during execution to prevent confusion under time pressure.
Quality Standard
  • A reader must understand Mission Success/Failure, End State, What the ME may/may not do, and What is out of scope without reading any other TMP section.
  • If the Mission section is vague, downstream sections will be vague or unstable (Effects, Tasks, Phasing, Contingencies).

2 - Environment​

Purpose

The Environment section identifies what the ME will operate within, what matters to mission success, and what limits or elevates execution risk. It describes the mission environment and terrain that shape execution feasibility, risk, and constraints.

2.1 - Required Information​

  • Mission Partner Context
    • How the mission partner operates
    • Known sensitivities or constraints that affect execution
    • Organizational or operational factors that shape coordination
  • Mission-Essential Functions
    • Functions that must not fail or be degraded
    • Functions that, if disrupted, create mission impact
  • Mission-Relevant Terrain
    • Systems, services, data, identities, and paths that enable mission-essential functions
    • Ownership and approval authority for mission-relevant terrain
    • Boundaries of terrain in scope vs out of scope
  • Dependencies and Single Points of Failure
    • Technical, operational, or organizational dependencies
    • Single points of failure that would create mission impact if disrupted
  • Authorities and Restrictions
    • What actions are permitted
    • What actions are restricted or prohibited
    • Approval requirements affecting execution
  • Network and System Characteristics
    • High-level network topology and segmentation
    • Operating systems and platforms relevant to execution
    • Protocols or technologies that introduce risk or limit visibility
  • Physical and Operational Constraints
    • Physical access limitations
    • Power, space, cooling, and deployment constraints
    • Planned maintenance windows or disruptions
  • Environmental Risks
    • Known instability or fragility in systems or processes
    • Actions likely to cause disruption or partner impact

2.2 - Supporting Artifacts​

  • Environment Diagrams: Logical mission partner environment diagrams (zones, trust boundaries, key dependencies)
  • Network/System Diagrams: Topology views relevant to access, visibility, and constraints
  • Deployment Diagrams: CVA/H deployment diagrams (if applicable)
Quality Standard
  • A reader must understand:
    • What terrain matters to mission success
    • What actions are feasible or infeasible
    • Where execution risk exists and why
  • The Environment section must directly inform:
    • Tactical task design
    • Execution phasing
    • Capability selection and MINFOR
    • Contingency development

3 - Enemy (Adversary Impact)​

Purpose

The Enemy section characterizes who the MPC is concerned about, what they are trying to achieve in this environment, and how their actions would impact mission success. This section exists to drive hunt prioritization, sensor placement, task focus, and contingency planning. It describes relevant adversary behavior as it applies to the mission environment and mission-relevant terrain.

3.1 - Required Information​

  • Relevant Adversaries
    • Adversary types or actors applicable to this mission
    • Why these adversaries are relevant to the mission partner and terrain
    • Exclusion of adversaries that do not influence planning decisions
  • Adversary Objectives
    • What the adversary is likely trying to achieve in this environment
    • Objectives framed in mission impact terms (not generic intent)
    • Alignment (or conflict) with mission partner operations
  • Adversary Capabilities and Limitations
    • Credible capabilities relevant to the terrain
    • Known limitations that constrain adversary options
    • Reliance on specific access vectors, infrastructure, or behaviors
  • Likely Avenues of Approach
    • How the adversary would most likely gain access
    • How they would move, persist, or operate within the environment
    • What terrain or dependencies they would leverage
  • Mission Impact Model
    • What happens if specific terrain, systems, or functions are compromised
    • How adversary actions translate into mission degradation or failure

3.2 - Past and Observed Activity​

  • Known Or Suspected Activity On:
    • The mission partner environment
    • Similar environments or mission sets
  • Patterns Or Trends That inform likely future behavior
  • No Data Statement If no relevant past activity is known

3.3 - Enemy Courses of Action (ECOAs)​

Purpose: Identify the adversary behaviors that matter most for planning and execution.

Only two ECOAs are required:

  • Most Likely COA
    • The lowest-risk, easiest path for the adversary to achieve objectives
    • Drives baseline hunt prioritization and sensor placement
  • Most Dangerous COA
    • The COA that would generate the greatest mission impact if successful
    • Drives early warning requirements and conservative contingency planning

Each COA must describe:

  • Entry Method
  • Key Actions On Terrain
  • Intended Effect
  • Resulting Mission Impact
Quality Standard
  • Threat content must be actionable and mission-driven.
  • A reader must be able to answer: “If the adversary does this, what breaks in the mission?”
  • If the Enemy section does not change hunt priorities, task design, phasing, or contingencies, it is not complete.
  • Generic threat summaries that do not influence decisions are unacceptable.

4 - Effects (Outcomes & Assessment)​

Purpose

The Effects section defines the outcomes the mission must produce in order to satisfy the tasking commander’s intent.

Effects describe what must change in the environment or adversary behavior as a result of CPT actions. This section ensures planning remains outcome-focused, Tactical Objectives (TOs) are justified, and assessment is meaningful and decision-relevant.

4.1 - Desired Effects​

Purpose: Identify the mission-relevant outcomes the CPT is expected to generate.

Required Information​

  • Outcome-Framed Effects: Desired effects stated as outcomes, not actions
  • CPT-Relevant Scope: Effects scoped to what the CPT can realistically influence
  • Mission Impact Terms: Effects expressed in mission impact terms (availability, integrity, confidence, decision advantage)
  • Environment/Enemy Alignment: Effects tied to the mission environment and adversary behavior

Standards​

  • TO Support: Each desired effect must be supported by one or more Tactical Objectives (TOs)
  • Assessability: Effects must be specific enough to support assessment

4.2 - Assessment Framework​

Purpose: Define how the MPC and execution elements will determine whether desired effects and objectives have been achieved.

Assessment connects execution outputs to mission outcomes and enables informed decision-making during execution and transition.

Measures of Effectiveness (MOEs)​

Purpose: Measure whether tactical objectives achieved the desired effect.

MOE Requirements​
  • TO Coverage: Each TO has at least one associated MOE
  • Outcome-Based: MOEs assess outcome, not activity
  • Decision Criteria: MOEs define criteria for Met / Unmet / Degraded
  • Evidence-Based: MOEs are evidence-based and decision-relevant

MOEs answer: “Did this objective change the environment or adversary behavior in the way intended?”

Measures of Performance (MOPs)​

Purpose: Measure whether tactical tasks were executed as required.

MOP Requirements​
  • TT Coverage: Each TT has at least one associated MOP
  • Observable: MOPs assess completion, quality, or coverage
  • Data Source: MOPs identify the data source used for measurement
  • Supports MOE: MOPs support MOEs but do not replace them

MOPs answer: “Was the task performed correctly and completely?”

4.3 - Assessment Traceability​

Purpose: Maintain traceability from mission intent through execution and assessment.

Required Information​

  • Clear linkage between:
    • Desired effects
    • TOs
    • MOEs
    • TTs
    • MOPs
  • Consistent identification and labeling across TOs, TTs, MOEs, and MOPs

4.4 - Assessment Planning​

Purpose: Describe how and when assessment will occur during execution.

Required Information​

  • Data Requirements: What data is required to assess MOEs and MOPs
  • Responsibilities: Who is responsible for assessment and reporting
  • Timing: When assessment occurs (continuous, event-based, phase-based)
  • Decision Support: How assessment informs decisions, transitions, or contingencies

Standards​

  • Feasibility: Assessment must be feasible with available access and tools
  • Validation: Assessment planning must be validated during the MPC and ROC
  • Decision-Relevant: Assessment must support decisions, not just reporting
Quality Standard
  • Effects must be clearly defined and assessable.
  • MOEs must enable decisions about mission success, adjustment, or termination.
  • If an effect cannot be assessed, it is not usable.
  • If assessment does not inform decisions, it is insufficient.

5 - Capabilities​

Purpose

The Capabilities section defines the forces, tools, systems, and access available to generate the desired effects — and the limits of those capabilities in the mission environment.

This section answers:

  • What capabilities are available?
  • What can they realistically do in this environment?
  • What mission effects degrade or fail if a capability is constrained or lost?

Capabilities defined here directly inform task feasibility, execution phasing, MINFOR, risk acceptance, and contingency planning.

5.1 - Forces​

Purpose: Identify personnel available to execute the mission and the roles they perform.

Required Information​

  • Mission Element (ME) composition
  • Roles and crew positions aligned to planned execution LOEs
  • Skill levels where relevant to execution quality or risk
  • Identification of roles requiring senior expertise
  • Identification of gaps that drive risk, timeline extension, or scope reduction

Standards​

  • Forces listed here must align with MINFOR and execution phasing
  • If a role is required for mission success, it must be reflected in contingencies

5.2 - Supporting Forces​

Purpose: Identify external forces or organizations required to support mission success.

Required Information​

  • Supporting unit or organization
  • Capability or function provided
  • Nature of support (continuous, on-call, conditional)
  • Coordination or deconfliction requirements

Standards​

  • Supporting forces critical to mission success must be treated as dependencies
  • Loss or unavailability of supporting forces must drive contingency planning

5.3 - Weapon System (Equipment and Software)​

Purpose: Identify equipment and software required to execute tasks and generate effects.

Required Information​

  • Equipment to be employed, including quantity and configuration
  • Mission-critical software, tools, or platforms
  • Identification of agent-based vs agentless tools
  • Capabilities that directly interact with mission partner systems
  • Known limitations or constraints affecting performance

Standards​

  • Loss of equipment or software below MINFOR must trigger contingencies
  • Capabilities listed here must be feasible within the defined environment

5.4 - Deviations​

Purpose: Capture deviations from baseline configurations that affect execution or risk.

Required Information​

  • Description of deviation
  • Whether the deviation touches mission partner networks
  • Approval authority and status
  • Operational impact of the deviation

Standards​

  • Deviations must be approved prior to execution
  • Unapproved deviations are unacceptable and invalidate execution assumptions

5.5 - MINFOR (Minimum Force)​

Purpose: Define the minimum personnel and equipment required to execute the mission without unacceptable risk.

Required Information​

  • Minimum personnel by role and skill level
  • Minimum equipment required
  • Alignment of MINFOR with concurrent execution LOEs
  • Conditions under which dropping below MINFOR results in mission failure or delay

Standards​

  • Dropping below MINFOR requires contingency execution or replanning
  • MINFOR must be validated during MPC execution and ROC

5.6 - Limiting Factors (LIMFACS)​

Purpose: Identify conditions that reduce the ability to generate desired effects.

Required Information​

  • Capability limitations or constraints
  • Description of how the limitation affects execution
  • Mission impact if the limitation is encountered

Standards​

  • LIMFACS must be realistic and observable
  • Each LIMFAC must inform risk acceptance or contingency planning
  • The absence of LIMFACS does not imply unlimited capability
Quality Standard
  • Capabilities must be evaluated against:
    • The mission environment
    • Adversary courses of action
    • Desired effects
  • If loss or degradation of a capability does not affect tasks, phasing, or contingencies, it does not belong in this section.
  • Assumed capability is a planning failure.

6 - Plan (Tactical Objectives and Tasks)​

Purpose

The Plan section translates Desired Effects, Environmental constraints, Enemy behavior, and Available Capabilities into executable Tactical Objectives (TOs) and Tactical Tasks (TTs).

This section converges all MPC LOE outputs into a coherent execution concept. The MPC owns the plan; the Mission Element (ME) executes it.

6.1 - Tactical Objectives (TOs)​

Purpose: Define the outcomes that must be achieved to generate the desired effects.

Required Information​

  • TO statements written as conditions achieved, not actions taken
  • TOs derived from desired effects and enemy impact considerations
  • TOs scoped to what the CPT can realistically influence
  • Clear linkage between TOs and desired effects

Standards​

  • TOs must be assessable via defined MOEs
  • TOs must not be written as disguised tasks
  • Each TO should be achievable through multiple supporting TTs
  • TOs that cannot be assessed or supported by tasks are invalid

6.2 - Tactical Tasks (TTs)​

Purpose: Provide executable direction to achieve tactical objectives.

Required Information (For Each TT)​

  • Task statement written as a clear action
  • Supported TO
  • Execution owner (element or role)
  • Dependencies (access, tools, approvals, coordination)
  • Constraints (time windows, restrictions, limitations)
  • Expected outputs or products
  • Associated MOP reference

Standards​

  • TTs must be executable without further planning by the ME
  • TTs must not direct the ME to “plan to” perform an action
  • Excessive specificity that removes execution flexibility should be avoided
  • Excessive vagueness that creates execution paralysis is unacceptable

6.3 - Task Organization​

Purpose: Organize TTs in a way that supports execution coherence and assessment.

Required Information​

  • Logical grouping of TTs under their supported TOs
  • Consistent numbering schema for:
    • TOs
    • TTs
    • MOEs
    • MOPs
  • Clear traceability from:
    • Desired effects → TOs → TTs → Assessment

Standards​

  • Numbering must remain consistent across TMP sections and assessment products
  • Assessment artifacts may be referenced rather than duplicated

6.4 - Technical Plans and Procedures​

Purpose: Reference detailed execution instructions without overloading the TMP.

Guidance​

  • Detailed procedures reside in technical sub-plans
  • TOs and TTs reference these plans; they do not duplicate them
  • Operators execute from technical plans, not from the TMP

Required Information​

  • List of referenced technical plans and procedures
  • Confirmation that referenced plans exist and are version-controlled

6.5 - Target Deliverables​

Purpose: Identify mission outputs, recipients, and delivery timelines.

Required Information​

  • Product name
  • Intended recipient(s)
  • Delivery timing or trigger

Standards​

  • Deliverables must align with commander expectations
  • Delivery timelines must be realistic and achievable during execution

6.6 - GO / NO-GO Criteria​

Purpose: Define minimum conditions required to initiate execution.

Required Information​

  • Personnel and equipment MINFOR status
  • Access and logistics readiness
  • Crew qualification and readiness considerations

Standards​

  • GO / NO-GO criteria are validated by the ME Lead upon receipt of the TMP
  • Conditions that degrade after GO must be addressed through contingencies
Quality Standard
  • The Plan must be executable without additional interpretation.
  • TOs must drive outcomes; TTs must drive action.
  • If the ME must redesign the plan to execute, the Plan section is insufficient.

7 - Phasing (Timing, Sequencing, and Execution Control)​

Purpose

The Phasing section controls when execution occurs, what can occur concurrently, and what must complete before other actions begin.

Phasing synchronizes execution Lines of Effort (LOEs) over time and events, enforces dependency management, ensures MINFOR realism, and enables controlled transitions and decision points during execution.

7.1 - Timeline​

Purpose: Provide a visual and authoritative representation of mission timing, phases, LOEs, and triggers.

Required Information​

  • Mission start and end points
  • Phase start and end points
  • Concurrent and sequential execution LOEs
  • Event-driven and decision-driven transitions
  • Critical milestones that gate execution

Standards​

  • A visual timeline is required
  • Timelines may be maintained in external artifacts (e.g., spreadsheet, diagram, planning tool)
  • The timeline must reflect:
    • Phase sequencing
    • Concurrent LOEs
    • Event-based transitions

7.2 - Phases and Triggers​

Purpose: Define how execution progresses through distinct phases and what causes transitions.

Required Information (Per Phase)​

  • Phase name and purpose
  • Phase start trigger:
    • Time-based
    • Event-based
    • Decision-based
  • Phase end trigger or exit condition
  • Active execution LOEs during the phase
  • Key decisions required during the phase
  • Assessment focus for the phase

Standards​

  • Every phase must have an explicit trigger
  • Event-driven actions should not rely solely on time-based triggers
  • Phases without clear triggers create uncontrolled execution

7.3 - Execution Lines of Effort (LOEs)​

Purpose: Define concurrent execution paths and how effort is organized during each phase.

Required Information (Per LOE)​

  • LOE name and purpose
  • Assigned personnel (by role)
  • Referenced Tactical Tasks (TTs)
  • Phase(s) in which the LOE is active

Standards​

  • Personnel are assigned to LOEs, not individual tasks
  • Individuals should not be assigned to concurrent LOEs unless explicitly planned
  • LOEs may disband and reform across phases as required
  • Concurrent LOEs determine personnel MINFOR

7.4 - Timeline Constraints​

Purpose: Anchor phasing to operational reality and known constraints.

Required Information​

  • Fixed start and end dates
  • Support availability windows
  • Maintenance or outage periods
  • External events affecting execution
  • Conditions that cause phase extension, regression, or termination

Standards​

  • Constraints must be reflected in the timeline and phase design
  • Known constraints must inform contingencies and decision points
Quality Standard
  • Phasing must clearly answer:
    • What happens when?
    • What must finish before something else starts?
    • What can occur in parallel?
    • Who must be available at the same time?
  • Weak phasing leads to idle time, double-tasking, missed decisions, and execution risk.

8 - Command, Control, and Contracts​

Purpose

This section defines how information, decisions, and actions flow during execution.

Contracts codify who communicates, when communication occurs, how it occurs, and what action follows. This section exists to prevent confusion, delay, or unauthorized action under time pressure.

If a decision or communication is time-sensitive or mission-critical, it must be captured here.

8.1 - Communication Contracts​

Purpose: Define how mission-critical information is communicated and what actions are taken when that information is passed.

Communication contracts ensure:

  • Common understanding across all participants
  • Timely decision-making
  • Controlled escalation
  • Accountability during execution

CACA Format​

All communication contracts will be written using the CACA format:

  • Condition: The event or observation that triggers the contract
  • Authority: Who confirms the condition and authorizes the communication
  • Communication: Medium, recipient, and required phrasing
  • Action: What the recipient does and how acknowledgment occurs
Standards​
  • Conditions must be observable
  • Authority must be explicit
  • Communication methods must include a PACE plan:
    • Primary
    • Alternate
    • Contingency
    • Emergency
  • Actions must be unambiguous and verifiable

8.2 - External Communication Contracts​

Purpose: Define communications with entities outside the Mission Element.

Required Information​

  • Mission-critical reporting triggers
  • Approval requests and escalation thresholds
  • Coordination with operations centers and mission partners
  • Required acknowledgments and response timelines

Standards​

  • External contracts are largely finalized by the MPC during planning
  • Contracts must align with authorities defined in orders and SPINS
  • Unauthorized external communication is prohibited

8.3 - DIRLAUTH (Direct Liaison Authorized)​

Purpose: Define who the Mission Element may communicate with directly without routing through an operations center.

Required Information​

  • Authorized entities for direct liaison
  • Scope and purpose of authorized communication
  • Explicit exclusions

Standards​

  • DIRLAUTH must be sourced from TASKORD/SPINS
  • Communication outside DIRLAUTH is a violation of orders
  • When in doubt, elevate rather than bypass command channels

8.4 - Points of Contact (POCs)​

Purpose: Ensure execution continuity and rapid coordination.

Required Information​

  • Primary and alternate points of contact for:
    • Command and control
    • Mission partner coordination
    • Technical support
    • Emergency response
  • Communication methods for each POC

Standards​

  • POCs must be reachable via approved communication paths
  • Gaps in POC coverage represent execution risk

8.5 - Internal Communication​

Purpose: Define internal Mission Element communication expectations during execution.

Required Information​

  • Primary internal communication mechanisms
  • Event types that require immediate elevation
  • Documentation requirements for deviations or significant events

Standards​

  • Internal communication procedures are owned by the Mission Element Lead
  • Existing unit SOPs may be referenced rather than duplicated
  • Internal communication must support situational awareness and accountability, not noise
Quality Standard
  • Communication contracts must be agreed upon by all involved parties prior to execution.
  • If a communication or decision path must be debated during execution, the TMP is incomplete.
  • Failure to define contracts shifts decision risk to the operator.

9 - Contingencies​

Purpose

The Contingencies section defines planned responses to anticipated failure, degradation, or change during execution.

Contingencies address what happens when assumptions prove false or execution conditions change. This section ensures the mission can continue, adapt, or terminate deliberately rather than reactively.

If an assumption exists without a contingency, the plan is incomplete.

9.1 - Contingency Planning​

Purpose: Identify realistic failure points and define deliberate responses.

Contingencies protect:

  • Mission timeline
  • Force safety
  • Commander trust

Standards​

  • All unvalidated or high-risk assumptions must have one or more contingencies
  • Contingencies must focus on conditions that materially impact:
    • Execution feasibility
    • Desired effects
    • Mission risk
  • Not all contingencies require immediate action, but all require acknowledgment and planning

9.2 - Contingency Plan​

Each contingency must include:

  • Trigger: An observable condition that indicates a change or failure
  • Impact: The operational effect on execution, LOEs, or objectives
  • Response: The deliberate action taken when the trigger is met

9.3 - Abort Criteria​

Purpose: Define conditions that require immediate termination of execution.

Abort criteria are rare, explicit, and non-negotiable. They protect authorities, safety, and mission partner trust.

Standards​

  • Abort triggers must be unambiguous
  • Authority to abort must be clearly defined
  • Abort actions must include disengagement and recovery actions
Quality Standard
  • Contingency triggers must be observable during execution.
  • Responses must be feasible with available capabilities.
  • If execution personnel must invent a response at runtime, the contingency is insufficient.
  • Abort criteria override all other execution guidance.